OCTRL-901 Document the order of actions performed during SOR and EOR #573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think we are at the stage where things have settled down and there is a finite number of changes expected to such a document (namely: removing BKP and Kafka plugins calls, possibly moving CCDB plugin calls). One could even consider filling the hooks automatically, based on the information parsed from
readout-dataflow.yaml
, but I would leave that for later.The reason for this document is also a request from users to know what are SOSOR, EOSOR, SOEOR, EOEOR timestamps exactly.